SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C#

C# static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C# code

  • All rules 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
 
Tags
    Impact
      Clean code attribute
        1. Using unsafe code blocks is security-sensitive

           Security Hotspot
        2. Not specifying a timeout for regular expressions is security-sensitive

           Security Hotspot
        3. Hard-coded secrets are security-sensitive

           Security Hotspot
        4. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        5. Deserializing objects without performing data validation is security-sensitive

           Security Hotspot
        6. Disabling ASP.NET "Request Validation" feature is security-sensitive

           Security Hotspot
        7. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        8. Using publicly writable directories is security-sensitive

           Security Hotspot
        9. Using clear-text protocols is security-sensitive

           Security Hotspot
        10. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        11. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        12. Configuring loggers is security-sensitive

           Security Hotspot
        13. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        14. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        15. Disabling CSRF protections is security-sensitive

           Security Hotspot
        16. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        17. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        18. Setting loose file permissions is security-sensitive

           Security Hotspot
        19. Using non-standard cryptographic algorithms is security-sensitive

           Security Hotspot
        20. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        21. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        22. Formatting SQL queries is security-sensitive

           Security Hotspot
        23. Hard-coded credentials are security-sensitive

           Security Hotspot
        24. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Using publicly writable directories is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe

        Operating systems have global directories where any user has write access. Those folders are mostly used as temporary storage areas like /tmp in Linux based systems. An application manipulating files from these folders is exposed to race conditions on filenames: a malicious user can try to create a file with a predictable name before the application does. A successful attack can result in other files being accessed, modified, corrupted or deleted. This risk is even higher if the application runs with elevated permissions.

        In the past, it has led to the following vulnerabilities:

        • CVE-2012-2451
        • CVE-2015-1838

        This rule raises an issue whenever it detects a hard-coded path to a publicly writable directory like /tmp (see examples bellow). It also detects access to environment variables that point to publicly writable directories, e.g., TMP, TMPDIR and TEMP.

        • /tmp
        • /var/tmp
        • /usr/tmp
        • /dev/shm
        • /dev/mqueue
        • /run/lock
        • /var/run/lock
        • /Library/Caches
        • /Users/Shared
        • /private/tmp
        • /private/var/tmp
        • \Windows\Temp
        • \Temp
        • \TMP
        • %USERPROFILE%\AppData\Local\Temp

        Ask Yourself Whether

        • Files are read from or written into a publicly writable folder
        • The application creates files with predictable names into a publicly writable folder

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        Out of the box, .NET is missing secure-by-design APIs to create temporary files. To overcome this, one of the following options can be used:

        • Use a dedicated sub-folder with tightly controlled permissions
        • Created temporary files in a publicly writable folder and make sure:
          • Generated filename is unpredictable
          • File is readable and writable only by the creating user ID
          • File descriptor is not inherited by child processes
          • File is destroyed as soon as it is closed

        Sensitive Code Example

        using var writer = new StreamWriter("/tmp/f"); // Sensitive
        
        var tmp = Environment.GetEnvironmentVariable("TMP"); // Sensitive
        

        Compliant Solution

        var randomPath = Path.Combine(Path.GetTempPath(), Path.GetRandomFileName());
        
        // Creates a new file with write, non inheritable permissions which is deleted on close.
        using var fileStream = new FileStream(randomPath, FileMode.CreateNew, FileAccess.Write, FileShare.None, 4096, FileOptions.DeleteOnClose);
        using var writer = new StreamWriter(fileStream);
        

        See

        • OWASP - Top 10 2021 Category A1 - Broken Access Control
        • OWASP - Top 10 2017 Category A5 - Broken Access Control
        • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
        • CWE - CWE-377 - Insecure Temporary File
        • CWE - CWE-379 - Creation of Temporary File in Directory with Incorrect Permissions
        • OWASP, Insecure Temporary File
        • STIG Viewer - Application Security and Development: V-222567 - The application must not be vulnerable to race conditions.
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use